\section{Team Structure}

The team adopted a laissez-faire structure, with regards to project management. The only specific role assigned was that of secretary. This role involved taking meeting minutes, and other administrative tasks. As outlined in the Contributions section in chapter 8, this role was fulfilled by a different person each semester. Beyond the project management structure, the team made use of the natural divide in the client-server architecture, and team members were allocating to each component as follows:

\begin{center}\begin{tabular}{| c | c |}
	 \hline
  Daniel & Server \\	 \hline
  Stephen & Server \\	 \hline
  David & Client \\	 \hline
  Agnieszka & Client \\	 \hline
  Ian & Client \\	 \hline
\end{tabular}
\end{center}
\section{Schedules}

\begin{figure}[ht!]

\centering	

	\includegraphics[scale=0.45]{images/gantt_init.png}
    \caption{Schedule}
    \end{figure}
		
Our schedule was drawn up as a Gantt chart in the early stages of the project, and is shown in figure B.1. This schedule included slack time within the requirements, design and evaluation stages, whereby the team would be divided to work on the overlapping tasks. The schedule was designed to give us an indication of when we had spent too long on a particular stage of the process, and to prompt us to move along. 

	\begin{figure}[ht!]

	\centering	

		\includegraphics[scale=0.45]{images/gantt_final.png}
	    \caption{Actual timings}
	    \end{figure}

Figure B.2 shows the actual timings of the project. As is clear from the chart, the implementation stage took far longer than anticipated. The intention was to implement a significant amount of the project over the Christmas break. While this was the case, the process of integrating the client network code with the client user interface was far more difficult than anticipated. These issues are detailed in chapter 7. This slippage during the implementation stage led to the testing and evaluation stages being postponed, and these stages were significantly shorter than planned. Further analysis of the project as a whole is contained within chapter 8.

\section{Version Control}

We made use of Google Code's Subversion hosting to store our project repository. While only one repository was maintained, there were discrete codebases for the client and server. This meant that each could be worked on in isolation. In addition to storing our code, we used this repository to store this dissertation.

We decided to make use of the interactive collaboration features provided by Google Docs when writing drafts of sections of this document. While version control systems manage multiple users editing the same document, this is not as interactive as Google Docs. While this introduced some issues with keeping our dissertation document synchronised with our Google Docs documents, these were minimal and significantly outweighed by the time gained in redrafting using Google Docs.